-
Notifications
You must be signed in to change notification settings - Fork 1
refactor: Repository 및 UseCase 구조 변경 #59
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- postLogin -> postAuthLogin - loginRequest(DTO) -> PostLoginRequest(DTO) - loginResponse(DTO) -> PostLoginResponse(DTO) - AuthUse�Case -> PostAuthLoginUseCase (usecase 하위 auth 패키지 생성) - LoginUseCase -> SocialLoginUseCase
- postReissue -> postAuthReissue - ReissueResponseDTO -> PostReissueResponseDTO
- getNicknameAvailability(SignUpService,Mapper, Repo) -> getAuthCheckNickname(AuthService, Mapper, Repo) - CheckNicknameResponse(DTO) -> GetCheckNicknameResponse(DTO) - SignUpUse�Case에서 GetAuthCheckNicknameUseCase로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
This reverts commit 3c2fc10.
- toUserProfileResponse -> toGetUserProfileResponse - 통신 response를 result 패턴으로 처리 - UserUseCase 제거 -> GetUserProfileUseCase 생성
- UserAdditionalInfoRequest, Response(DTO) -> PostUserAdditionalInfoRequest, Response(DTO) - SignUpUse�Case에서 PostUserAdditionalInfoUseCase로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- postBoardWrite(BoardWriteService, Mapper, Repo) -> postBoard(BoardService, Mapper, Repo) - BoardWriteRequest, Request(DTO) -> PostBoardRequest, Response(DTO) - BoardWriteUse�Case에서 PostBoardUseCase로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- boardEdit(BoardWriteService, Mapper, Repo) -> putBoard(BoardService, Mapper, Repo) - BoardEditRequest, Request(DTO) -> PutBoardRequest, Response(DTO) - BoardWriteUse�Case 제거 -> PutBoardUseCase 생성 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- getBoardList(BoardListService, Mapper, Repo) -> getBoardPaging(BoardService, Mapper, Repo) - BoardListRequest, Request(DTO) -> GetBoardPagingRequest, Response(DTO) - BoardListUse�Case 제거 -> GetBoardPagingUseCase 생성 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- getBoard(BoardReadService, Mapper, Repo) -> getBoard(BoardService, Mapper, Repo) - BoardReadRequest, Request(DTO) -> GetBoardRequest, Response(DTO) - BoardReadUse�Case 에서 GetBoardUseCase 로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- deleteBoard(BoardReadService, Mapper, Repo) -> deleteBoard(BoardService, Mapper, Repo) - BoardDeleteRequest, Request(DTO) -> DeleteBoardRequest, Response(DTO) - BoardReadUse�Case 제거 -> DeleteBoardUseCase 생성 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- postBoardLike 이동 (BoardLikeService, Mapper, Repo) -> (BoardService, Mapper, Repo) - BoardLikeUse�Case 에서 PostBoardLikeUseCase 로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- getBoardLikedList (BoardLikeService, Mapper, Repo) -> getLikedBoard (BoardService, Mapper, Repo) - BoardLikeUse�Case 제거 및 GetLikedBoardUseCase 로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- EnrollResponse, Request(DTO) -> PostEnrollResponse, Request(DTO) - postEnroll 함수를 EnrollUse�Case 에서 PostEnrollUseCase 로 이동 - 통신 response를 Result 패턴으로 처리해 Reissue 에러 발생 시 예외처리
- HTTP Request 방식 Post -> Patch 수정 - Enroll Service, Mapper, Repo의 postEnrollCancel -> patchEnrollReject - EnrollCancelResponse(DTO) -> PatchEnrollRejectResponse(DTO) - EnrollUseCase 제거 및 PatchEnrollRejectUseCase 생성
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
작업 내용